Skip to content

Conversation

@jtp10181
Copy link

@jtp10181 jtp10181 commented Jan 3, 2026

Type of Change

  • WWST Certification Request
    • If this is your first time contributing code:
      • I have reviewed the README.md file
      • I have reviewed the CODE_OF_CONDUCT.md file
      • I have signed the CLA
    • I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com
  • Bug fix
  • New feature
  • Refactor

Checklist

  • I have performed a self-review of my code
  • I have commented my code in hard-to-understand areas
  • I have verified my changes by testing with a device or have communicated a plan for testing
  • I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change

  • Adding profile for ZSE42 for WWST Certification
  • Added sub_driver to handle populating firmwareUpdate.currentVersion
  • Added ability to set battery quantity and type in configurations

Summary of Completed Tests

  • Tested all features manually
  • Passed full integration test from the developer test suite

* Added sub_driver to handle populating firmewareUpdate.currentVersion
* Added ability to set battery quantity and type in configurations
@jtp10181 jtp10181 changed the title Add ZSE42 to zwave-sensor (for WWST Cert) Add Zooz ZSE42 to zwave-sensor (for WWST Cert) Jan 3, 2026
Copy link
Contributor

@greens greens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless you're gating some functionality based on the firmware version, the sub-driver seems unneeded (outside of the additions to configurations).

@greens greens changed the title Add Zooz ZSE42 to zwave-sensor (for WWST Cert) WWSTCERT-9861 Add Zooz ZSE42 to zwave-sensor (for WWST Cert) Jan 14, 2026
@jtp10181
Copy link
Author

jtp10181 commented Jan 14, 2026

Unless you're gating some functionality based on the firmware version, the sub-driver seems unneeded (outside of the additions to configurations).

it is needed for troubleshooting by Zooz support. The customer needs to be able to see the firmware version of the device.

We will also be adding more sensors to this driver which need the same firmware version functionality, which is why I made it as a special sub driver just for the firmware version feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants